Skip to content

Correct docker-compose handling for containers that don't publish their superserver port #1613

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 15, 2025

Conversation

gjsjohnmurray
Copy link
Contributor

This PR fixes #1606

@gjsjohnmurray gjsjohnmurray merged commit b5f1df6 into intersystems-community:master Jul 15, 2025
5 checks passed
@gjsjohnmurray gjsjohnmurray deleted the fix-1606 branch July 15, 2025 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

objectscript.conn.docker-compose feature fails if container doesn't expose its superserver port
2 participants